feat: add flow compilation verification at worker startup #474
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This was referenced Dec 1, 2025
Contributor
Author
This was referenced Dec 1, 2025
|
View your CI Pipeline Execution ↗ for commit 7b1db0a
☁️ Nx Cloud last updated this comment at |
jumski
force-pushed
the
12-01-add_flow_compilation_at_worker_startup_with_sql_direct_call
branch
from
1bef6d0 to
f98a265
Compare
jumski
force-pushed
the
12-01-add_flow_compilation_at_worker_startup_with_sql_direct_call
branch
from
f98a265 to
c5ef186
Compare
Contributor
🔍 Preview Deployment: Website✅ Deployment successful! 🔗 Preview URL: https://pr-474.pgflow.pages.dev 📝 Details:
_Last updated: _ |
jumski
force-pushed
the
11-30-add_local_supabase_detection_to_controlplane_for_auto_mode_detection
branch
from
170589a to
cc15d3c
Compare
jumski
force-pushed
the
12-01-add_flow_compilation_at_worker_startup_with_sql_direct_call
branch
from
c5ef186 to
196bef5
Compare
Contributor
Merge activity
|
# Flow Compilation at Worker Startup This PR adds automatic flow compilation and verification during worker startup. When a flow worker starts, it now ensures the flow is properly compiled in the database before processing any tasks. Key features: - Adds `ensureFlowCompiled` method to the Queries class to check flow compilation status - Implements flow compilation during worker startup in the `FlowWorkerLifecycle` class - Adds environment detection to determine compilation mode (development vs production) - Introduces `FlowShapeMismatchError` for handling flow structure mismatches - In development mode (local Supabase), mismatched flows are automatically recompiled - In production mode, mismatches throw errors to prevent unexpected behavior The PR includes comprehensive integration tests covering: - Compiling new flows on worker startup - Verifying existing flows with matching structure - Handling mismatches in production mode (throws error) - Recompiling mismatched flows in development mode This ensures flows are always properly compiled before execution, preventing runtime errors from mismatched flow definitions.
graphite-app
bot
force-pushed
the
11-30-add_local_supabase_detection_to_controlplane_for_auto_mode_detection
branch
from
cc15d3c to
5e255c3
Compare
graphite-app
bot
force-pushed
the
12-01-add_flow_compilation_at_worker_startup_with_sql_direct_call
branch
from
196bef5 to
7b1db0a
Compare
graphite-app
bot
changed the base branch from
11-30-add_local_supabase_detection_to_controlplane_for_auto_mode_detection
to
main
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Flow Compilation at Worker Startup
This PR adds automatic flow compilation and verification during worker startup. When a flow worker starts, it now ensures the flow is properly compiled in the database before processing any tasks.
Key features:
ensureFlowCompiledmethod to the Queries class to check flow compilation statusFlowWorkerLifecycleclassFlowShapeMismatchErrorfor handling flow structure mismatchesThe PR includes comprehensive integration tests covering:
This ensures flows are always properly compiled before execution, preventing runtime errors from mismatched flow definitions.